Build out Highlight component to auto format, consolidate global code styling #80
+117
−71
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Build out the
Highlight
component so that it can work with both:Highlight
to tell it what language to use in this case)gatsby-transformer-remark
). This format appears to be a standard and it seems to work well withPrismjs
which is the syntax highlighting library in use in this repo. No language required as a prop since the data is already in the markup.In the process, I noticed some duplication in the global styles that we are exporting for styling
pre
andcode
blocks. Those styles have since been moved to theHighlight
component.Heads up @jonniebigodes since I know you were potentially going to be looking at this component.